{% extends "base.html" %}
{# Copyright The IETF Trust 2015, All Rights Reserved #}
{% load origin %}
{% load static %}
{% load django_bootstrap5 %}
{% load ietf_filters %}
{% load textfilters %}
{% block title %}Status update for {{ group.acronym }} {{ group.type.name }}{% endblock %}
{% block content %}
    {% origin %}
    <h1>
        Status update for {{ group.type.name }}
        <br>
        <small class="text-body-secondary">{{ group.acronym }}</small>
    </h1>
    {% if can_provide_status_update %}
        <div class="my-3 alert alert-info">
            <h2>About Status Updates</h2>
            <p>
                Capturing group status updates in the datatracker allows including them in meeting proceedings. This capability was added to address the IESG request at
                <a href="https://github.com/ietf-tools/datatracker/issues/1773">ticket 1773</a>.
                Not all groups are expected to provide status updates. Those that do have historically sent messages by email or have placed them on a wiki. For example, see
                <a href="https://mailarchive.ietf.org/arch/msg/saag/fo2b3KA47SM4MuQuYj5VIh-Tjok">
                    the Kitten report sent to SAAG for IETF94
                </a>
                or the
                <a href="https://wiki.ietf.org/group/rtg/IETF94summary">Routing area high level summaries for IETF94</a>.
            </p>
        </div>
    {% endif %}
    <pre class="border p-3 my-3 pasted">{{ status_update.desc|default:"(none)"|urlize_ietf_docs|linkify }}</pre>
    {% if can_provide_status_update %}
        <a id="edit_button"
           class="btn btn-primary"
           href="{% url "ietf.group.views.group_about_status_edit" acronym=group.acronym %}">
            Edit
        </a>
    {% endif %}
    <a class="btn btn-secondary float-end"
       href="{% url "ietf.group.views.group_about" acronym=group.acronym %}">Back</a>
{% endblock %}